-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enhanced API #162
Enhanced API #162
Conversation
filiptypjeu
commented
Aug 5, 2023
•
edited
Loading
edited
- Made API available to all logged in users. This resolves issue Open up API to other than admins #145.
- Changed how the default model APIs are serialized.
- Added Filters to APIs (that takes into account if you are staff or not)
- Added Order filters to APIs
- Added Search filters to APIs
- Added Pagination to APIs
- Added ~127 tests for the APIs
- Moved log file path to .env. This resolves issue Move log file path to .env file #124.
- Fixed how initials are handled for combined names. This resolves issue Fix given_names to initials conversion for combined names #161.
- Made the Model view APIs accessible to all logged in users. - Added test for all Model view APIs.
…ed tests for testing it.
… added Filters to all API endpoints.
…selects all related objects.
… to admin page navbar.
… public, API and HTK-dump pages.
… Groups etc.) in the detail views (not in the list views).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice work!
Is it be possible to allow for non-superusers to view the root api page (/api) without giving access to any additional api routes? Could be useful allow for users to be able to just access /api and choose the relevant route from there. The few people that actually need to access the API (bosse/htk...) can be given direct links so if it's not trivial to implement it's probably more than good enough as it is.
…bobject counts as properties on the respective Model.